Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfd89b186b2489fdbcdf15a7de8e9e73c3e564516d2f9927721ae9fcb6d36135

Tx prefix hash: 404d8a62df1a7626cfc12c6b488ce3dc1a9c4fef5790a3b9dcf34aa7cd53a0bb
Tx public key: 26f8c4e4369dba932f972eb17b24b712ebeaad588d1b81ac0d747a6122bd7ac2
Timestamp: 1696623759 Timestamp [UCT]: 2023-10-06 20:22:39 Age [y:d:h:m:s]: 01:180:18:01:07
Block: 863966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390217 RingCT/type: yes/0
Extra: 0126f8c4e4369dba932f972eb17b24b712ebeaad588d1b81ac0d747a6122bd7ac2021100000004faf35c9c000000000000000000

1 output(s) for total of 0.842019266000 dcy

stealth address amount amount idx
00: 46848ecc3fb8c379a829aeca7b35f97a667b451aba57fa4ddb81fe9fb16b166d 0.842019266000 1318468 of 0

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": 863976, "vin": [ { "gen": { "height": 863966 } } ], "vout": [ { "amount": 842019266, "target": { "key": "46848ecc3fb8c379a829aeca7b35f97a667b451aba57fa4ddb81fe9fb16b166d" } } ], "extra": [ 1, 38, 248, 196, 228, 54, 157, 186, 147, 47, 151, 46, 177, 123, 36, 183, 18, 235, 234, 173, 88, 141, 27, 129, 172, 13, 116, 122, 97, 34, 189, 122, 194, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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