Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd2ef4046a2d7a22057f2eeb5a67ebe56de74518178246985e53665df3d37cd

Tx prefix hash: dc0e2d19150cf65dbd516fd730eee7416a0af7e0b143c3d6eaa2f8ee2c62ea78
Tx public key: 6c1bf23c903e22e8d3e786c2b378930d5d6bea9e37a12abcfcad65f700900244
Timestamp: 1710396289 Timestamp [UCT]: 2024-03-14 06:04:49 Age [y:d:h:m:s]: 01:032:23:07:39
Block: 977954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284534 RingCT/type: yes/0
Extra: 016c1bf23c903e22e8d3e786c2b378930d5d6bea9e37a12abcfcad65f7009002440211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 333da5f6ba501e96faa572db735b11327000b22060a699a2ac848fe403b33ac9 0.600000000000 1437963 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": 977964, "vin": [ { "gen": { "height": 977954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "333da5f6ba501e96faa572db735b11327000b22060a699a2ac848fe403b33ac9" } } ], "extra": [ 1, 108, 27, 242, 60, 144, 62, 34, 232, 211, 231, 134, 194, 179, 120, 147, 13, 93, 107, 234, 158, 55, 161, 42, 188, 252, 173, 101, 247, 0, 144, 2, 68, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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