Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b096830eed6e64bfbacec03d7cd5ce391e17a01302ca5123b2fddd54f6aee6e

Tx prefix hash: 609d90dce2aa4d03f408ab3ecf8db8137ef348682825b30c17dc650be4f4cfd0
Tx public key: 04c30b5cf9187cc5ca7ecc252c317ec54724533c8b8beaa14a04e0d8344aff12
Timestamp: 1718167016 Timestamp [UCT]: 2024-06-12 04:36:56 Age [y:d:h:m:s]: 00:297:17:54:21
Block: 1042366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212767 RingCT/type: yes/0
Extra: 0104c30b5cf9187cc5ca7ecc252c317ec54724533c8b8beaa14a04e0d8344aff120211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe8df075293f29833d9a29ae0791b02ea6f4570ab0dd140938c57974876c230 0.600000000000 1511267 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": 1042376, "vin": [ { "gen": { "height": 1042366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe8df075293f29833d9a29ae0791b02ea6f4570ab0dd140938c57974876c230" } } ], "extra": [ 1, 4, 195, 11, 92, 249, 24, 124, 197, 202, 126, 204, 37, 44, 49, 126, 197, 71, 36, 83, 60, 139, 139, 234, 161, 74, 4, 224, 216, 52, 74, 255, 18, 2, 17, 0, 0, 0, 1, 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