Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51bfdcdb55d03fd77843ba62c2baa0873e9c6b4f491eb437bb423d62e88c02a2

Tx prefix hash: 64a1aa089cb424e37e778531b8cacd53ff344e6807c1e8c3f7be2cced273360a
Tx public key: e696ba77762add5a776f718e95d6700271fd4973cb56b4d6c687acc294a324e5
Timestamp: 1737552175 Timestamp [UCT]: 2025-01-22 13:22:55 Age [y:d:h:m:s]: 00:146:12:54:04
Block: 1202881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104474 RingCT/type: yes/0
Extra: 01e696ba77762add5a776f718e95d6700271fd4973cb56b4d6c687acc294a324e5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c60d7ed38853ab09d1cde94fd61e0f4b582ef41407bd067c0920cc56826a380b 0.600000000000 1689548 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": 1202891, "vin": [ { "gen": { "height": 1202881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c60d7ed38853ab09d1cde94fd61e0f4b582ef41407bd067c0920cc56826a380b" } } ], "extra": [ 1, 230, 150, 186, 119, 118, 42, 221, 90, 119, 111, 113, 142, 149, 214, 112, 2, 113, 253, 73, 115, 203, 86, 180, 214, 198, 135, 172, 194, 148, 163, 36, 229, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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