Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160935f8abb750efe77e28060e0f9bdc01c4976f2afaffa9b5ec735dbc96919c

Tx prefix hash: 1f58c6d53f6ea3fdcca1df51e59496cf3e7bcd5216a25bfbce5e54dc9cb4d69f
Tx public key: 3e11218eda1f6f25c0c9d7990c945e7ae1bba1bb180e36941f9910f09869366f
Timestamp: 1578075984 Timestamp [UCT]: 2020-01-03 18:26:24 Age [y:d:h:m:s]: 04:364:11:27:32
Block: 37895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149770 RingCT/type: yes/0
Extra: 013e11218eda1f6f25c0c9d7990c945e7ae1bba1bb180e36941f9910f09869366f021100000009d81c26c0000000000000000000

1 output(s) for total of 459.662404739000 dcy

stealth address amount amount idx
00: 3d126c207f1a7344dc7ac2094317bf09dcf44d463dbe33b8dd20b3b9b08d721d 459.662404739000 64440 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": 37905, "vin": [ { "gen": { "height": 37895 } } ], "vout": [ { "amount": 459662404739, "target": { "key": "3d126c207f1a7344dc7ac2094317bf09dcf44d463dbe33b8dd20b3b9b08d721d" } } ], "extra": [ 1, 62, 17, 33, 142, 218, 31, 111, 37, 192, 201, 215, 153, 12, 148, 94, 122, 225, 187, 161, 187, 24, 14, 54, 148, 31, 153, 16, 240, 152, 105, 54, 111, 2, 17, 0, 0, 0, 9, 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