Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8864e38a2e824c43a858973ca8a233688d3164f275ed3db7e04a8c6cedb56207

Tx prefix hash: 036845fca176875d63a6b9bb096b956b590e9ef8f45b298ff023fbc0de1e20d0
Tx public key: 33b226cbf2e24aa41a3f17439c811d0e9d11b24e43f89a5d5dd5363a34cf6ef5
Timestamp: 1700846048 Timestamp [UCT]: 2023-11-24 17:14:08 Age [y:d:h:m:s]: 01:166:22:41:53
Block: 898758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380496 RingCT/type: yes/0
Extra: 0133b226cbf2e24aa41a3f17439c811d0e9d11b24e43f89a5d5dd5363a34cf6ef502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.645716136000 dcy

stealth address amount amount idx
00: b95ca5530ddeada21c9d72d0057e166c455d8012ef75ac11dbfb6bf4900f5383 0.645716136000 1355193 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": 898768, "vin": [ { "gen": { "height": 898758 } } ], "vout": [ { "amount": 645716136, "target": { "key": "b95ca5530ddeada21c9d72d0057e166c455d8012ef75ac11dbfb6bf4900f5383" } } ], "extra": [ 1, 51, 178, 38, 203, 242, 226, 74, 164, 26, 63, 23, 67, 156, 129, 29, 14, 157, 17, 178, 78, 67, 248, 154, 93, 93, 213, 54, 58, 52, 207, 110, 245, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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