Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9db126206764b482b4720e8edbf988ab3e694e357b09781fbc2c899089b314e

Tx prefix hash: ff3c6b0672f044da7eadac1cac227db5f3a679a48b65d352d6af46ea362c38c4
Tx public key: 0c1197cde80dcd36fbd6fc0d458f22e27876082dadd989dc3490dcc30bb048c4
Timestamp: 1577722179 Timestamp [UCT]: 2019-12-30 16:09:39 Age [y:d:h:m:s]: 05:152:13:08:26
Block: 35151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1258823 RingCT/type: yes/0
Extra: 010c1197cde80dcd36fbd6fc0d458f22e27876082dadd989dc3490dcc30bb048c4021100000002d81c26c0000000000000000000

1 output(s) for total of 469.386937879000 dcy

stealth address amount amount idx
00: 2e19b345c19723735c64454947e6e896291b033b87b79039e99cce40fd0c8edc 469.386937879000 59212 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": 35161, "vin": [ { "gen": { "height": 35151 } } ], "vout": [ { "amount": 469386937879, "target": { "key": "2e19b345c19723735c64454947e6e896291b033b87b79039e99cce40fd0c8edc" } } ], "extra": [ 1, 12, 17, 151, 205, 232, 13, 205, 54, 251, 214, 252, 13, 69, 143, 34, 226, 120, 118, 8, 45, 173, 217, 137, 220, 52, 144, 220, 195, 11, 176, 72, 196, 2, 17, 0, 0, 0, 2, 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