Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebcd7ec6f9e30ba5d87f54971fa0447daccae172d4a5d893a2c0c64a3814bad4

Tx prefix hash: 49966abd6ed4b1f0963fd85bc6e7ce2350cd0a5a92c19adb97faf9966cc64f7c
Tx public key: 57c2725955eb5c891a388b02592b56a7b259e495e571f3aa48d6f5361749a019
Timestamp: 1702976880 Timestamp [UCT]: 2023-12-19 09:08:00 Age [y:d:h:m:s]: 01:120:20:01:14
Block: 916435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347484 RingCT/type: yes/0
Extra: 0157c2725955eb5c891a388b02592b56a7b259e495e571f3aa48d6f5361749a019021100000005c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24fcfc61f003fd9d5a1c0c935112fd1b6f65da26636f7768995dd7ebbe6046f9 0.600000000000 1373985 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": 916445, "vin": [ { "gen": { "height": 916435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24fcfc61f003fd9d5a1c0c935112fd1b6f65da26636f7768995dd7ebbe6046f9" } } ], "extra": [ 1, 87, 194, 114, 89, 85, 235, 92, 137, 26, 56, 139, 2, 89, 43, 86, 167, 178, 89, 228, 149, 229, 113, 243, 170, 72, 214, 245, 54, 23, 73, 160, 25, 2, 17, 0, 0, 0, 5, 197, 69, 41, 96, 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