Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f677edf298cd20bd3e8d0be4d3788709b1020648e0c946824124c95212d3e5e2

Tx prefix hash: 4f735309c63238816a83870313d52eb4e069acaa2d7973f5e54d3b96c3296482
Tx public key: 588ee547c0e8371fc22a7f04785e51afa7bb9fdaecbe2c9090d03e82a043ea7b
Timestamp: 1728933978 Timestamp [UCT]: 2024-10-14 19:26:18 Age [y:d:h:m:s]: 00:244:09:02:07
Block: 1131628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174378 RingCT/type: yes/0
Extra: 01588ee547c0e8371fc22a7f04785e51afa7bb9fdaecbe2c9090d03e82a043ea7b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5db836aa7755c415f40b6d417d785fcd8004340c21ffe9ca1b3bae9e21e6d78d 0.600000000000 1614531 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": 1131638, "vin": [ { "gen": { "height": 1131628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5db836aa7755c415f40b6d417d785fcd8004340c21ffe9ca1b3bae9e21e6d78d" } } ], "extra": [ 1, 88, 142, 229, 71, 192, 232, 55, 31, 194, 42, 127, 4, 120, 94, 81, 175, 167, 187, 159, 218, 236, 190, 44, 144, 144, 208, 62, 130, 160, 67, 234, 123, 2, 17, 0, 0, 0, 1, 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