Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b663a1c99a05eb26536c6f01b559bc09b51a5af4e4ae3f31e1e397ca7e4bb2d3

Tx prefix hash: e9facd1c73e186272733afdfdcd7626895b9092c4ab961b0d6dcead965ab34d5
Tx public key: d7fce5a897efaffe16af9f5e9ef9f04298117df7448aac01c81cadcb7957bbf6
Timestamp: 1577579033 Timestamp [UCT]: 2019-12-29 00:23:53 Age [y:d:h:m:s]: 05:005:07:10:28
Block: 33928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153794 RingCT/type: yes/0
Extra: 01d7fce5a897efaffe16af9f5e9ef9f04298117df7448aac01c81cadcb7957bbf602110000000fd81c26c0000000000000000000

1 output(s) for total of 473.787183475000 dcy

stealth address amount amount idx
00: a75900ebdf833e9ca40a4393a71d5df6efbecfbf34d8ccd1b3efb43a7cef68c1 473.787183475000 57037 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": 33938, "vin": [ { "gen": { "height": 33928 } } ], "vout": [ { "amount": 473787183475, "target": { "key": "a75900ebdf833e9ca40a4393a71d5df6efbecfbf34d8ccd1b3efb43a7cef68c1" } } ], "extra": [ 1, 215, 252, 229, 168, 151, 239, 175, 254, 22, 175, 159, 94, 158, 249, 240, 66, 152, 17, 125, 247, 68, 138, 172, 1, 200, 28, 173, 203, 121, 87, 187, 246, 2, 17, 0, 0, 0, 15, 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