Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f268163cb67e2e7d1e56ebdef5fc9bc939d7d743400c3ef82df0750110fe2cd4

Tx prefix hash: 1a3af6b72f4cde20255a4acdeff4a8b19196b483b4be40e560f7a01191d5cc85
Tx public key: e6ce8a08ec86691b593d38f2c3baad7ba1156dbe3f54aa12aad41d65dcbf7b04
Timestamp: 1725065466 Timestamp [UCT]: 2024-08-31 00:51:06 Age [y:d:h:m:s]: 00:222:04:44:48
Block: 1099550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158662 RingCT/type: yes/0
Extra: 01e6ce8a08ec86691b593d38f2c3baad7ba1156dbe3f54aa12aad41d65dcbf7b04021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb4a268e06e964068ece45289ad1d5026408b82000ead07faead0b1f02e70430 0.600000000000 1575513 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": 1099560, "vin": [ { "gen": { "height": 1099550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb4a268e06e964068ece45289ad1d5026408b82000ead07faead0b1f02e70430" } } ], "extra": [ 1, 230, 206, 138, 8, 236, 134, 105, 27, 89, 61, 56, 242, 195, 186, 173, 123, 161, 21, 109, 190, 63, 84, 170, 18, 170, 212, 29, 101, 220, 191, 123, 4, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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