Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39be47eb933856f5b0dc227d5e0b5b229451081b17febd68ba2b3339b1c2e04e

Tx prefix hash: bc273f89f863a1b3e2929d44e1ca58e38b0e1892606f247bf2303fc006abbc64
Tx public key: d3bfa0676ebc9a9f4c0b822e149b35943295fea739ebe01b787bee5d11b282a9
Timestamp: 1703316091 Timestamp [UCT]: 2023-12-23 07:21:31 Age [y:d:h:m:s]: 01:144:21:47:36
Block: 919238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364697 RingCT/type: yes/0
Extra: 01d3bfa0676ebc9a9f4c0b822e149b35943295fea739ebe01b787bee5d11b282a90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b720294c3a9edb2d7770da04a4a0812bd476f82cec17b86a2bcce14ae548975d 0.600000000000 1376904 of 15

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": 919248, "vin": [ { "gen": { "height": 919238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b720294c3a9edb2d7770da04a4a0812bd476f82cec17b86a2bcce14ae548975d" } } ], "extra": [ 1, 211, 191, 160, 103, 110, 188, 154, 159, 76, 11, 130, 46, 20, 155, 53, 148, 50, 149, 254, 167, 57, 235, 224, 27, 120, 123, 238, 93, 17, 178, 130, 169, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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