Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79a10ddfdb1c5da010d460032fb7dddc27619429b4355e87a7e13ecb0121e592

Tx prefix hash: 3f02df062e7e41e8e9bf3752f08c8e345baf475654b8296b3a055da87ee955a8
Tx public key: 70e3c4b2d0d4d1d6ca7a123d8e5cb00901bbdf28a02a676a6b7f3d31fc2f9d6a
Timestamp: 1733857057 Timestamp [UCT]: 2024-12-10 18:57:37 Age [y:d:h:m:s]: 00:108:14:35:38
Block: 1172341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77404 RingCT/type: yes/0
Extra: 0170e3c4b2d0d4d1d6ca7a123d8e5cb00901bbdf28a02a676a6b7f3d31fc2f9d6a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9427dd2b777ecd82503379f2241b0103dbe4a924b4148d9b4300bfc87ef1c7 0.600000000000 1658220 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": 1172351, "vin": [ { "gen": { "height": 1172341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9427dd2b777ecd82503379f2241b0103dbe4a924b4148d9b4300bfc87ef1c7" } } ], "extra": [ 1, 112, 227, 196, 178, 208, 212, 209, 214, 202, 122, 18, 61, 142, 92, 176, 9, 1, 187, 223, 40, 160, 42, 103, 106, 107, 127, 61, 49, 252, 47, 157, 106, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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