Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38df908e95233e3cac6d02c578926185106b0ff4041d24fe114cdcd01321b9e7

Tx prefix hash: 18cbde913b4a0e7984abae43d8059417841807f4447cd572dc85027242d73181
Tx public key: d56b5d973a65d3eec05e95b1680ae8d9a09803c9db894aa889bbb3c4364edb79
Timestamp: 1703281944 Timestamp [UCT]: 2023-12-22 21:52:24 Age [y:d:h:m:s]: 01:317:08:23:18
Block: 918959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485644 RingCT/type: yes/0
Extra: 01d56b5d973a65d3eec05e95b1680ae8d9a09803c9db894aa889bbb3c4364edb790211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f1d0fd6ecf8a2e03f24000e53a80643a33f062264d70841ca25ccb189909b99 0.600000000000 1376623 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": 918969, "vin": [ { "gen": { "height": 918959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f1d0fd6ecf8a2e03f24000e53a80643a33f062264d70841ca25ccb189909b99" } } ], "extra": [ 1, 213, 107, 93, 151, 58, 101, 211, 238, 192, 94, 149, 177, 104, 10, 232, 217, 160, 152, 3, 201, 219, 137, 74, 168, 137, 187, 179, 196, 54, 78, 219, 121, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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