Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7d8233c376f18e692679d84d1c4d7b8ca8f04f02d3f11d97afedf232d626f70

Tx prefix hash: 42c8022961b4e5ba08865164ea260a4e65e5f97afc1566b87dde4974f92a9118
Tx public key: f2cbf9566dbbce96623f5c6dc0481c0b851731e99cb3049d6436ffa062345cb0
Timestamp: 1713098714 Timestamp [UCT]: 2024-04-14 12:45:14 Age [y:d:h:m:s]: 01:023:19:22:35
Block: 1000324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277992 RingCT/type: yes/0
Extra: 01f2cbf9566dbbce96623f5c6dc0481c0b851731e99cb3049d6436ffa062345cb0021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 551d769ef26469deb9796b3f76a65cbfff9522bfdc0e2b70cadca9ebce4cf451 0.600000000000 1460822 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": 1000334, "vin": [ { "gen": { "height": 1000324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "551d769ef26469deb9796b3f76a65cbfff9522bfdc0e2b70cadca9ebce4cf451" } } ], "extra": [ 1, 242, 203, 249, 86, 109, 187, 206, 150, 98, 63, 92, 109, 192, 72, 28, 11, 133, 23, 49, 233, 156, 179, 4, 157, 100, 54, 255, 160, 98, 52, 92, 176, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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