Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66319ca6f68bc86858e0922ba2866156d75bc2d29bba0e10566ab3c8918208f0

Tx prefix hash: 1357e61bd90d1794ce3785b4e29f61df8eff46d6329f1a24830876d7b913a7d5
Tx public key: 33a6aea379f877c5c8a4f3996610890173f29cdfef15f61f09375a6075d0faf8
Timestamp: 1674094556 Timestamp [UCT]: 2023-01-19 02:15:56 Age [y:d:h:m:s]: 02:285:22:53:23
Block: 677837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723760 RingCT/type: yes/0
Extra: 0133a6aea379f877c5c8a4f3996610890173f29cdfef15f61f09375a6075d0faf8021100000001faf35c9c000000000000000000

1 output(s) for total of 3.483730744000 dcy

stealth address amount amount idx
00: 6b756d8699c350583bbcc7b2c9036bf97d08a1d98f58bf3f58b09b5d2f96c1cc 3.483730744000 1119632 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": 677847, "vin": [ { "gen": { "height": 677837 } } ], "vout": [ { "amount": 3483730744, "target": { "key": "6b756d8699c350583bbcc7b2c9036bf97d08a1d98f58bf3f58b09b5d2f96c1cc" } } ], "extra": [ 1, 51, 166, 174, 163, 121, 248, 119, 197, 200, 164, 243, 153, 102, 16, 137, 1, 115, 242, 156, 223, 239, 21, 246, 31, 9, 55, 90, 96, 117, 208, 250, 248, 2, 17, 0, 0, 0, 1, 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