Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56c72efdfd6e69dee85fa0cd3a2095e7573b8ef440818a32beffccb3549b87a

Tx prefix hash: b56f6c848cb52733fb904ce98b6fa86cea67f15562c2debb2eb92a8571d76561
Tx public key: 0ee2af50f40def888e39b3a6519545939912b4fd8c948bcf7dd77d6c5cedfb9e
Timestamp: 1709397728 Timestamp [UCT]: 2024-03-02 16:42:08 Age [y:d:h:m:s]: 01:081:18:37:40
Block: 969665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319484 RingCT/type: yes/0
Extra: 010ee2af50f40def888e39b3a6519545939912b4fd8c948bcf7dd77d6c5cedfb9e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86c5a0aafb9b4d7b1c64d4ff7072da829d00f9339d8f2448e6eabc6081e4b4d 0.600000000000 1429502 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": 969675, "vin": [ { "gen": { "height": 969665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86c5a0aafb9b4d7b1c64d4ff7072da829d00f9339d8f2448e6eabc6081e4b4d" } } ], "extra": [ 1, 14, 226, 175, 80, 244, 13, 239, 136, 142, 57, 179, 166, 81, 149, 69, 147, 153, 18, 180, 253, 140, 148, 139, 207, 125, 215, 125, 108, 92, 237, 251, 158, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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