Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780bde1cd695e57a4656f01b87074fd62b8a018468b1032db85ed51440bb4091

Tx prefix hash: 34849e2f3300b5af9a3841f0a70ecde6630b2286b2b9d4516fee5d89fa773c27
Tx public key: aaedf3d706dd237cf244316415e2a990d90c1cfa41cf12c960e64d3f2d9d0b7e
Timestamp: 1729727404 Timestamp [UCT]: 2024-10-23 23:50:04 Age [y:d:h:m:s]: 00:159:09:48:51
Block: 1138171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113712 RingCT/type: yes/0
Extra: 01aaedf3d706dd237cf244316415e2a990d90c1cfa41cf12c960e64d3f2d9d0b7e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6727dfc59c112a4e3a09d14a21a3ed5391988184f4fc0411c502319e484d62eb 0.600000000000 1621788 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": 1138181, "vin": [ { "gen": { "height": 1138171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6727dfc59c112a4e3a09d14a21a3ed5391988184f4fc0411c502319e484d62eb" } } ], "extra": [ 1, 170, 237, 243, 215, 6, 221, 35, 124, 242, 68, 49, 100, 21, 226, 169, 144, 217, 12, 28, 250, 65, 207, 18, 201, 96, 230, 77, 63, 45, 157, 11, 126, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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