Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cdfa773007358556456de5fc80f7b5dad28db797844b9199573e95103cab8b4

Tx prefix hash: fc1f3c374f4ba0e32032d0b37c6ce3a9df3df9ff38991fb92c8c9a9b11490746
Tx public key: fcb81ce4c87b161df66007e85b499574b80a47cb91beeeb0199be5ef4c344a39
Timestamp: 1697075321 Timestamp [UCT]: 2023-10-12 01:48:41 Age [y:d:h:m:s]: 02:114:12:09:27
Block: 867699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601394 RingCT/type: yes/0
Extra: 01fcb81ce4c87b161df66007e85b499574b80a47cb91beeeb0199be5ef4c344a3902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.818376302000 dcy

stealth address amount amount idx
00: b31df7af9e0cf20c0f458a3361b221ee3e9e37fb1e299c6f05e7c427b19c0797 0.818376302000 1322407 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": 867709, "vin": [ { "gen": { "height": 867699 } } ], "vout": [ { "amount": 818376302, "target": { "key": "b31df7af9e0cf20c0f458a3361b221ee3e9e37fb1e299c6f05e7c427b19c0797" } } ], "extra": [ 1, 252, 184, 28, 228, 200, 123, 22, 29, 246, 96, 7, 232, 91, 73, 149, 116, 184, 10, 71, 203, 145, 190, 238, 176, 25, 155, 229, 239, 76, 52, 74, 57, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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