Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 581c1f51bebe4243b4884aa325a4e329aa01fac3cde95834aea0a1b556732908

Tx prefix hash: be676b47bfa2166914dbbbf776a4b4c496f089f25b0ba2a7ba7ce92c86e5bce3
Tx public key: 973ec4134b9fdd6211170e894a4da78b4e1529b4dc47b141ccedb81c7bdca9b3
Timestamp: 1696006722 Timestamp [UCT]: 2023-09-29 16:58:42 Age [y:d:h:m:s]: 01:151:23:30:29
Block: 858842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369646 RingCT/type: yes/0
Extra: 01973ec4134b9fdd6211170e894a4da78b4e1529b4dc47b141ccedb81c7bdca9b30211000000064b8f5122000000000000000000

1 output(s) for total of 0.875588352000 dcy

stealth address amount amount idx
00: 6519726bfbe0e439cc56ef445a309f976bae51e84f80510040228dfc81f95883 0.875588352000 1313038 of 0

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": 858852, "vin": [ { "gen": { "height": 858842 } } ], "vout": [ { "amount": 875588352, "target": { "key": "6519726bfbe0e439cc56ef445a309f976bae51e84f80510040228dfc81f95883" } } ], "extra": [ 1, 151, 62, 196, 19, 75, 159, 221, 98, 17, 23, 14, 137, 74, 77, 167, 139, 78, 21, 41, 180, 220, 71, 177, 65, 204, 237, 184, 28, 123, 220, 169, 179, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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