Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a175b54704a9570dae450e1eb076b14083fc7f615ead3d2daa0918a8eb9f57a7

Tx prefix hash: a286cb015cde921876b08af1dc192b20e3cf2f85d124d6ea58b41b31169fdc70
Tx public key: eefcb1ffffbeb9eb28ac74d6ddba8229f267908430e47bb40e835b51183e3584
Timestamp: 1730171879 Timestamp [UCT]: 2024-10-29 03:17:59 Age [y:d:h:m:s]: 01:013:03:16:07
Block: 1141834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267782 RingCT/type: yes/0
Extra: 01eefcb1ffffbeb9eb28ac74d6ddba8229f267908430e47bb40e835b51183e35840211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c25a00f65a00bb207f4cf50d5c6addecc56ec0ccef7c3c852e8de96ecd7c47 0.600000000000 1625665 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": 1141844, "vin": [ { "gen": { "height": 1141834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c25a00f65a00bb207f4cf50d5c6addecc56ec0ccef7c3c852e8de96ecd7c47" } } ], "extra": [ 1, 238, 252, 177, 255, 255, 190, 185, 235, 40, 172, 116, 214, 221, 186, 130, 41, 242, 103, 144, 132, 48, 228, 123, 180, 14, 131, 91, 81, 24, 62, 53, 132, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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