Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 007ce60f3e08980a9f9df0150b1987722c11832dfd6d6eddfd74777dc0a8700f

Tx prefix hash: bc52a008495e4ee01e47a5ae8967c48011a10872a3ee498a0383b43a2b530bd8
Tx public key: dc2e9f6b3022af37935041aaca423cfbcecbd643ac1dc9878492c00ec3d31829
Timestamp: 1730543685 Timestamp [UCT]: 2024-11-02 10:34:45 Age [y:d:h:m:s]: 00:147:02:52:48
Block: 1144880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104976 RingCT/type: yes/0
Extra: 01dc2e9f6b3022af37935041aaca423cfbcecbd643ac1dc9878492c00ec3d318290211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d794f6779178380b3d46c6cfd91e196a8a535da0f8b603bc6c45d083080971 0.600000000000 1629217 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": 1144890, "vin": [ { "gen": { "height": 1144880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d794f6779178380b3d46c6cfd91e196a8a535da0f8b603bc6c45d083080971" } } ], "extra": [ 1, 220, 46, 159, 107, 48, 34, 175, 55, 147, 80, 65, 170, 202, 66, 60, 251, 206, 203, 214, 67, 172, 29, 201, 135, 132, 146, 192, 14, 195, 211, 24, 41, 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