Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 474c860d4982b10902d6be0bb0c0852828b7acabd2dcd141cbdff0e994f20db1

Tx prefix hash: 6b1e82610dc4861f7e61c91ff70406de36302328c7f70f2c4912af25d7cbfe51
Tx public key: 47971bd0183979b5d96a80612c162ef6fad5d535b0bd1570bbed495d3edfff1d
Timestamp: 1724327687 Timestamp [UCT]: 2024-08-22 11:54:47 Age [y:d:h:m:s]: 00:184:02:41:18
Block: 1093450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131390 RingCT/type: yes/0
Extra: 0147971bd0183979b5d96a80612c162ef6fad5d535b0bd1570bbed495d3edfff1d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a21698960e5efba3501d848287df6c1f379ea3d2391dbdb1cf7533d5b0f0ed8c 0.600000000000 1568397 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": 1093460, "vin": [ { "gen": { "height": 1093450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a21698960e5efba3501d848287df6c1f379ea3d2391dbdb1cf7533d5b0f0ed8c" } } ], "extra": [ 1, 71, 151, 27, 208, 24, 57, 121, 181, 217, 106, 128, 97, 44, 22, 46, 246, 250, 213, 213, 53, 176, 189, 21, 112, 187, 237, 73, 93, 62, 223, 255, 29, 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