Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6177807b2fd7b1eff718441dfb51171c7f7a855b80b0a25d4ec900200640202c

Tx prefix hash: fd428b029e4a1658a3c112011e08d176018f6c652ef1161465468a6d952148f2
Tx public key: d0cb9cd1d134d294e9847c15d9663a2f17c9f4a8d1cf7942f29c5291cbcc6cc8
Timestamp: 1743287316 Timestamp [UCT]: 2025-03-29 22:28:36 Age [y:d:h:m:s]: 00:229:07:41:36
Block: 1250134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161622 RingCT/type: yes/0
Extra: 01d0cb9cd1d134d294e9847c15d9663a2f17c9f4a8d1cf7942f29c5291cbcc6cc80211000000069ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fc2967aa62ad5f2481cadb6856e52e4667bf4ffebffd24ca94ee01826a20073 0.600000000000 1737181 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": 1250144, "vin": [ { "gen": { "height": 1250134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fc2967aa62ad5f2481cadb6856e52e4667bf4ffebffd24ca94ee01826a20073" } } ], "extra": [ 1, 208, 203, 156, 209, 209, 52, 210, 148, 233, 132, 124, 21, 217, 102, 58, 47, 23, 201, 244, 168, 209, 207, 121, 66, 242, 156, 82, 145, 203, 204, 108, 200, 2, 17, 0, 0, 0, 6, 155, 166, 41, 223, 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