Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc4dd0c6c3aff943fc67cb9f303e38c785e1e473f4ad10d7e5f65b5b8a80825

Tx prefix hash: bc52f4b9c51440d0b4e2f2c88e2722fffd316da2342717cac912a4b5ecbab6d4
Tx public key: 1731c71f13abe4e8e83a535a4850e45de78fc45bdb32da8151ed7b7059f0d6d3
Timestamp: 1637973978 Timestamp [UCT]: 2021-11-27 00:46:18 Age [y:d:h:m:s]: 02:359:01:18:32
Block: 382890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774627 RingCT/type: yes/0
Extra: 011731c71f13abe4e8e83a535a4850e45de78fc45bdb32da8151ed7b7059f0d6d302110000000c536c63bb000000000000000000

1 output(s) for total of 33.061827932000 dcy

stealth address amount amount idx
00: d18dfeca3e24e7426ba6144e4f045ebd4e3ed5c0f37972c58a541258b49a598a 33.061827932000 773145 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": 382900, "vin": [ { "gen": { "height": 382890 } } ], "vout": [ { "amount": 33061827932, "target": { "key": "d18dfeca3e24e7426ba6144e4f045ebd4e3ed5c0f37972c58a541258b49a598a" } } ], "extra": [ 1, 23, 49, 199, 31, 19, 171, 228, 232, 232, 58, 83, 90, 72, 80, 228, 93, 231, 143, 196, 91, 219, 50, 218, 129, 81, 237, 123, 112, 89, 240, 214, 211, 2, 17, 0, 0, 0, 12, 83, 108, 99, 187, 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