Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac260184eeecfd3bd1e512417bdbccb6b8d1ff6499fbab16a71df1ab540901de

Tx prefix hash: ef9106be4d037333afbb886d69d277d7381c3cfa16fef30fe60e9bb5500595a1
Tx public key: 976423b911cad9881317af2d8df1de766f25a041285efced9d40420516df58b5
Timestamp: 1578932813 Timestamp [UCT]: 2020-01-13 16:26:53 Age [y:d:h:m:s]: 05:024:11:20:22
Block: 44803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167575 RingCT/type: yes/0
Extra: 01976423b911cad9881317af2d8df1de766f25a041285efced9d40420516df58b5021100000008d81c26c0000000000000000000

1 output(s) for total of 436.071187398000 dcy

stealth address amount amount idx
00: 8b3ef44abfeae3e54152f0985bdf70e61eb05800eb1c797d8d68f31be4c76d6c 436.071187398000 81642 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": 44813, "vin": [ { "gen": { "height": 44803 } } ], "vout": [ { "amount": 436071187398, "target": { "key": "8b3ef44abfeae3e54152f0985bdf70e61eb05800eb1c797d8d68f31be4c76d6c" } } ], "extra": [ 1, 151, 100, 35, 185, 17, 202, 217, 136, 19, 23, 175, 45, 141, 241, 222, 118, 111, 37, 160, 65, 40, 94, 252, 237, 157, 64, 66, 5, 22, 223, 88, 181, 2, 17, 0, 0, 0, 8, 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