Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4f15f39cf7fac1ddcf422d2d140628758e3dc797b6f32863c0313277438ffc08

Tx prefix hash: 0d290d326ac67c558e16f05de0bb59dc60a54bae13d13b1324a998acd2d942ca
Tx public key: 077feceb00e062abdb1ccc53e30c6bb4cbcfff591c755e851c25380a6c08221a
Timestamp: 1725698137 Timestamp [UCT]: 2024-09-07 08:35:37 Age [y:d:h:m:s]: 00:106:20:29:22
Block: 1104801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76442 RingCT/type: yes/0
Extra: 01077feceb00e062abdb1ccc53e30c6bb4cbcfff591c755e851c25380a6c08221a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e52a8e99d0b2a586407f0e1d44d5591af73f00cd7ac80a7843c01ab77af60c1 0.600000000000 1582080 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1104811, "vin": [ { "gen": { "height": 1104801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e52a8e99d0b2a586407f0e1d44d5591af73f00cd7ac80a7843c01ab77af60c1" } } ], "extra": [ 1, 7, 127, 236, 235, 0, 224, 98, 171, 219, 28, 204, 83, 227, 12, 107, 180, 203, 207, 255, 89, 28, 117, 94, 133, 28, 37, 56, 10, 108, 8, 34, 26, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8