Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfe400a92076084907a1a2312bb53fb2e241b50b2a7f6b6bce626b6e6698cf08

Tx prefix hash: ceef8efabb5d367598c62505540b5ae2f7d1b6fa4bb4457267df99b0b1615f7a
Tx public key: 1b724b789bda45e81d8432de2a81df79112aa67bf3be38b9bd1fc544c008b471
Timestamp: 1737566063 Timestamp [UCT]: 2025-01-22 17:14:23 Age [y:d:h:m:s]: 00:150:01:00:08
Block: 1202987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106938 RingCT/type: yes/0
Extra: 011b724b789bda45e81d8432de2a81df79112aa67bf3be38b9bd1fc544c008b471021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 218e74a5559fd0b8f628c09d2a11049bdcc8d935efac447a0b99285cfc74f7af 0.600000000000 1689658 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": 1202997, "vin": [ { "gen": { "height": 1202987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "218e74a5559fd0b8f628c09d2a11049bdcc8d935efac447a0b99285cfc74f7af" } } ], "extra": [ 1, 27, 114, 75, 120, 155, 218, 69, 232, 29, 132, 50, 222, 42, 129, 223, 121, 17, 42, 166, 123, 243, 190, 56, 185, 189, 31, 197, 68, 192, 8, 180, 113, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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