Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7bee2de7b094b849e9dc2a4efa87132ffd6be090bee6dde948b1e445308afb4

Tx prefix hash: c499d1227753759196f10a5112cc5ae48f1caf373df8be5e8660de8bf8b56aa0
Tx public key: 5c2d359b5de25692e9667da0ec57d9198acd85a8b9dc65e4621306ab7dce443e
Timestamp: 1724937477 Timestamp [UCT]: 2024-08-29 13:17:57 Age [y:d:h:m:s]: 00:216:18:48:27
Block: 1098492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154782 RingCT/type: yes/0
Extra: 015c2d359b5de25692e9667da0ec57d9198acd85a8b9dc65e4621306ab7dce443e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d634ff66dba20a89824b56f80a57810ad85ae4616b4245f7cfb5d14d993b669 0.600000000000 1574225 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": 1098502, "vin": [ { "gen": { "height": 1098492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d634ff66dba20a89824b56f80a57810ad85ae4616b4245f7cfb5d14d993b669" } } ], "extra": [ 1, 92, 45, 53, 155, 93, 226, 86, 146, 233, 102, 125, 160, 236, 87, 217, 25, 138, 205, 133, 168, 185, 220, 101, 228, 98, 19, 6, 171, 125, 206, 68, 62, 2, 17, 0, 0, 0, 1, 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