Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fd0bca9025a48cc0d087b8d361bc06b30a4934635ddff02060ea4c96ef6130

Tx prefix hash: 2904181f1f8edb988a7b8036c6f411d517490af7e512d3ef3d5d5d45d81dead8
Tx public key: e58303d7bec6ecf59132811ba4b5f807f55a1e26f197a4ee06d2886fb6dbf048
Timestamp: 1710235486 Timestamp [UCT]: 2024-03-12 09:24:46 Age [y:d:h:m:s]: 01:246:03:00:45
Block: 976619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434608 RingCT/type: yes/0
Extra: 01e58303d7bec6ecf59132811ba4b5f807f55a1e26f197a4ee06d2886fb6dbf0480211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a2a20d97f3231c2ae36e4ad3a1da2956e6a2c5ff0c873eb2125f4bd996f831a 0.600000000000 1436614 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": 976629, "vin": [ { "gen": { "height": 976619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a2a20d97f3231c2ae36e4ad3a1da2956e6a2c5ff0c873eb2125f4bd996f831a" } } ], "extra": [ 1, 229, 131, 3, 215, 190, 198, 236, 245, 145, 50, 129, 27, 164, 181, 248, 7, 245, 90, 30, 38, 241, 151, 164, 238, 6, 210, 136, 111, 182, 219, 240, 72, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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