Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519435860abe3989c90ebbb8c6f242dbe5723e843c9d6ee64ac26249dfe69ef2

Tx prefix hash: 329ca205c30d065aa5fc6fbcbaf6e5e082e55e9ee931f1fa570430ec2eec229c
Tx public key: 9e7439ada9c33f6f44a0967535cbf1204dd3a3d67237ba04aee5955f3212c44d
Timestamp: 1728385081 Timestamp [UCT]: 2024-10-08 10:58:01 Age [y:d:h:m:s]: 00:250:00:46:48
Block: 1127070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178440 RingCT/type: yes/0
Extra: 019e7439ada9c33f6f44a0967535cbf1204dd3a3d67237ba04aee5955f3212c44d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fb70b63d5235dc7c09177c938cfed9f0408ff6b6ca512b75241bcf1c5bdde6f 0.600000000000 1609869 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": 1127080, "vin": [ { "gen": { "height": 1127070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fb70b63d5235dc7c09177c938cfed9f0408ff6b6ca512b75241bcf1c5bdde6f" } } ], "extra": [ 1, 158, 116, 57, 173, 169, 195, 63, 111, 68, 160, 150, 117, 53, 203, 241, 32, 77, 211, 163, 214, 114, 55, 186, 4, 174, 229, 149, 95, 50, 18, 196, 77, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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