Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e750d185835d36aa5e0ac191d7fa39c0613de90bbce21a47a41cd42bc8f14f7

Tx prefix hash: 5b17070326c9ae2b0eae1ecefa3c37ab0721ef08da7983ae447a6c385674ebc6
Tx public key: 8686fb44d94d36f065631c344e0dce15173312ddff9f302e7749ab6707c22818
Timestamp: 1719926282 Timestamp [UCT]: 2024-07-02 13:18:02 Age [y:d:h:m:s]: 00:145:11:31:46
Block: 1056943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104111 RingCT/type: yes/0
Extra: 018686fb44d94d36f065631c344e0dce15173312ddff9f302e7749ab6707c228180211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 401c83fd18f3214adf0b8909f88e16efe49f6fdae4f00dccfef5ccb216ad048e 0.600000000000 1527372 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": 1056953, "vin": [ { "gen": { "height": 1056943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "401c83fd18f3214adf0b8909f88e16efe49f6fdae4f00dccfef5ccb216ad048e" } } ], "extra": [ 1, 134, 134, 251, 68, 217, 77, 54, 240, 101, 99, 28, 52, 78, 13, 206, 21, 23, 51, 18, 221, 255, 159, 48, 46, 119, 73, 171, 103, 7, 194, 40, 24, 2, 17, 0, 0, 0, 4, 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