Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31a8d62a909d2fc32bbc6645fb16ffecfd0f14408113d85230aa531268c03254

Tx prefix hash: 67b1a73d752077001de564d8a47e2100e87d7171ee4831fbf398eaf64edca798
Tx public key: ed0b1adf3664dc9ea55249500eda403a1fc19185d4639bf054b48c8a6bf1c38d
Timestamp: 1574753288 Timestamp [UCT]: 2019-11-26 07:28:08 Age [y:d:h:m:s]: 05:073:11:37:38
Block: 17728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195100 RingCT/type: yes/0
Extra: 01ed0b1adf3664dc9ea55249500eda403a1fc19185d4639bf054b48c8a6bf1c38d021100000001f95225a5000000000000000000

1 output(s) for total of 536.118331007000 dcy

stealth address amount amount idx
00: e30f33f8baa10d2f4cefc8910e106221923228ea2cf15fccf3eb11d36a3c4bf9 536.118331007000 26192 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": 17738, "vin": [ { "gen": { "height": 17728 } } ], "vout": [ { "amount": 536118331007, "target": { "key": "e30f33f8baa10d2f4cefc8910e106221923228ea2cf15fccf3eb11d36a3c4bf9" } } ], "extra": [ 1, 237, 11, 26, 223, 54, 100, 220, 158, 165, 82, 73, 80, 14, 218, 64, 58, 31, 193, 145, 133, 212, 99, 155, 240, 84, 180, 140, 138, 107, 241, 195, 141, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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