Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa06d18e29cb3ea84b321bad184978b0296fe77ce379a1a1a3b766f7b4cbd65c

Tx prefix hash: 5b3cb8514a55763d1e160c16ab894d935bc867e1c270cc2c0c31e6e656ce3b91
Tx public key: a7950409431d8c6d2580c9002b155e65fabc03507d89f8ed2cbac75179266fe0
Timestamp: 1729844378 Timestamp [UCT]: 2024-10-25 08:19:38 Age [y:d:h:m:s]: 01:042:21:07:46
Block: 1139130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289070 RingCT/type: yes/0
Extra: 01a7950409431d8c6d2580c9002b155e65fabc03507d89f8ed2cbac75179266fe002110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 005caae2e4c49ecaedc0c3b071a9eb0722e70a85eea788c8dff9138bfa444d2e 0.600000000000 1622895 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": 1139140, "vin": [ { "gen": { "height": 1139130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "005caae2e4c49ecaedc0c3b071a9eb0722e70a85eea788c8dff9138bfa444d2e" } } ], "extra": [ 1, 167, 149, 4, 9, 67, 29, 140, 109, 37, 128, 201, 0, 43, 21, 94, 101, 250, 188, 3, 80, 125, 137, 248, 237, 44, 186, 199, 81, 121, 38, 111, 224, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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