Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6b4924e03720c54e13399c71fa426dc271221eb3e012f260baf505851668c3

Tx prefix hash: ea514522b912b90c345322db621e0de219f2d52c2a1d40a66529f9906ad0794b
Tx public key: 3dda4f191d1346f15b5611bdd9ed661d5a6579334eaecc8b9c8f76aa016636d2
Timestamp: 1724292279 Timestamp [UCT]: 2024-08-22 02:04:39 Age [y:d:h:m:s]: 00:268:15:46:06
Block: 1093151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191893 RingCT/type: yes/0
Extra: 013dda4f191d1346f15b5611bdd9ed661d5a6579334eaecc8b9c8f76aa016636d2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e73b41d2df55a3a9292a123b460d3e832599bfcd55e2f1e0d704b20de8f4341c 0.600000000000 1568038 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": 1093161, "vin": [ { "gen": { "height": 1093151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e73b41d2df55a3a9292a123b460d3e832599bfcd55e2f1e0d704b20de8f4341c" } } ], "extra": [ 1, 61, 218, 79, 25, 29, 19, 70, 241, 91, 86, 17, 189, 217, 237, 102, 29, 90, 101, 121, 51, 78, 174, 204, 139, 156, 143, 118, 170, 1, 102, 54, 210, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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