Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65498b9ac493b63e14f06ce64c1d8403d688359ce10fa753ed1b73ae9d1e4aaf

Tx prefix hash: f922949e01e133910e9f47415864b287edec1beedd1c999cda9ba1ae7d0ecd3c
Tx public key: bc1d71ce2c43f72a310115a344f2c29212f69399ae608089d90e487a96330118
Timestamp: 1722476455 Timestamp [UCT]: 2024-08-01 01:40:55 Age [y:d:h:m:s]: 00:242:01:02:08
Block: 1078084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172880 RingCT/type: yes/0
Extra: 01bc1d71ce2c43f72a310115a344f2c29212f69399ae608089d90e487a96330118021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ded51932d7e374c83a0ed7f3368acdef4d31010e02f5f6c4484b803a6933fea2 0.600000000000 1550647 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": 1078094, "vin": [ { "gen": { "height": 1078084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ded51932d7e374c83a0ed7f3368acdef4d31010e02f5f6c4484b803a6933fea2" } } ], "extra": [ 1, 188, 29, 113, 206, 44, 67, 247, 42, 49, 1, 21, 163, 68, 242, 194, 146, 18, 246, 147, 153, 174, 96, 128, 137, 217, 14, 72, 122, 150, 51, 1, 24, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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