Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aee580f6935dcdcf87eec38978feac697410c8c4603edf6b613480633bb9ed2

Tx prefix hash: 4ce3db1565b5aa8450a75e576cde01c8a9f6eb4bcd85e01a33ca3f3a8a26a1ac
Tx public key: ce9651df22072737d46e4b095ece807548d4e305624309dd381f6735f823a7e9
Timestamp: 1729536486 Timestamp [UCT]: 2024-10-21 18:48:06 Age [y:d:h:m:s]: 00:171:13:56:49
Block: 1136575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122446 RingCT/type: yes/0
Extra: 01ce9651df22072737d46e4b095ece807548d4e305624309dd381f6735f823a7e90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e040b9b3e5f0fa380c8b7c8fbe43903c8158dd7bb0862e9c6c361e815e6272 0.600000000000 1619922 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": 1136585, "vin": [ { "gen": { "height": 1136575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e040b9b3e5f0fa380c8b7c8fbe43903c8158dd7bb0862e9c6c361e815e6272" } } ], "extra": [ 1, 206, 150, 81, 223, 34, 7, 39, 55, 212, 110, 75, 9, 94, 206, 128, 117, 72, 212, 227, 5, 98, 67, 9, 221, 56, 31, 103, 53, 248, 35, 167, 233, 2, 17, 0, 0, 0, 2, 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