Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efe735b810ec51fe7aabf78429e734dfe4508b0cd9bab82c19d8602c621bee31

Tx prefix hash: ff85466544fc82e098e4b7093129cb4609f3c89a386f8fa52957b1fdfbc53de9
Tx public key: 4a3a58dc480cb326a22c337134feec02137ce9d88b294d39a90e981f3de222c5
Timestamp: 1577996552 Timestamp [UCT]: 2020-01-02 20:22:32 Age [y:d:h:m:s]: 05:000:11:19:14
Block: 37409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150315 RingCT/type: yes/0
Extra: 014a3a58dc480cb326a22c337134feec02137ce9d88b294d39a90e981f3de222c5021100000004d81c26c0000000000000000000

1 output(s) for total of 461.369950665000 dcy

stealth address amount amount idx
00: 2cc08f0b8b1ea2393e64c2940b4a70011bed2fd13b02cd9ca1e3d5a093697eca 461.369950665000 63495 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": 37419, "vin": [ { "gen": { "height": 37409 } } ], "vout": [ { "amount": 461369950665, "target": { "key": "2cc08f0b8b1ea2393e64c2940b4a70011bed2fd13b02cd9ca1e3d5a093697eca" } } ], "extra": [ 1, 74, 58, 88, 220, 72, 12, 179, 38, 162, 44, 51, 113, 52, 254, 236, 2, 19, 124, 233, 216, 139, 41, 77, 57, 169, 14, 152, 31, 61, 226, 34, 197, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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