Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b0b2f7a5dce268114ee933652fe1b34e9eef4ca8c4041b7c5370ce5ba29c3b3

Tx prefix hash: 9ce16fcd939bfe89d130efddc595b8a585dc38cded77718ab4706fcf22e21396
Tx public key: bc42ab2779ef617fd4bf9981df8dd0f3ec764f92d6e36b0a8272d65a4720a397
Timestamp: 1764300885 Timestamp [UCT]: 2025-11-28 03:34:45 Age [y:d:h:m:s]: 00:025:10:57:17
Block: 1421702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18218 RingCT/type: yes/0
Extra: 01bc42ab2779ef617fd4bf9981df8dd0f3ec764f92d6e36b0a8272d65a4720a3970211000000054e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7f23463db8b72ca4b1034ce40b1b0e5d4f98b1154ca9275dab4541427fe235 0.600000000000 1910259 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": 1421712, "vin": [ { "gen": { "height": 1421702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7f23463db8b72ca4b1034ce40b1b0e5d4f98b1154ca9275dab4541427fe235" } } ], "extra": [ 1, 188, 66, 171, 39, 121, 239, 97, 127, 212, 191, 153, 129, 223, 141, 208, 243, 236, 118, 79, 146, 214, 227, 107, 10, 130, 114, 214, 90, 71, 32, 163, 151, 2, 17, 0, 0, 0, 5, 78, 123, 252, 9, 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