Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4d605689d4803c4c6d73d0909417362ab1616a7409ae59b35edba6326646a7

Tx prefix hash: a6b25ac3a4c2d6e43cd9b97e7009ff89fae636e7e2e8970508c0cfe3606f505e
Tx public key: 569f7e09324a3477e1d798d286b3cc98058d7aec4f0de05f1115f4d38241fefa
Timestamp: 1699302048 Timestamp [UCT]: 2023-11-06 20:20:48 Age [y:d:h:m:s]: 01:148:16:48:13
Block: 885961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367464 RingCT/type: yes/0
Extra: 01569f7e09324a3477e1d798d286b3cc98058d7aec4f0de05f1115f4d38241fefa02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.711940060000 dcy

stealth address amount amount idx
00: e18a2deab7659ecac5f0b8da0b8f282d7e33d41cb5860706d7dc974624e5011b 0.711940060000 1341760 of 0

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": 885971, "vin": [ { "gen": { "height": 885961 } } ], "vout": [ { "amount": 711940060, "target": { "key": "e18a2deab7659ecac5f0b8da0b8f282d7e33d41cb5860706d7dc974624e5011b" } } ], "extra": [ 1, 86, 159, 126, 9, 50, 74, 52, 119, 225, 215, 152, 210, 134, 179, 204, 152, 5, 141, 122, 236, 79, 13, 224, 95, 17, 21, 244, 211, 130, 65, 254, 250, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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