Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4b266f56dab7e2e607daa94897043ce9d9df55c2906cbc64e15a40786ff312

Tx prefix hash: b6d53fac2d3389fb060b358f770c59cf98b4a7836a6d8f91b5ecdac198096b6d
Tx public key: 4d3df6e69dbf0658d55680ba6e18b40234d9c3b1506c8d7e89a2be29a0eb1dde
Timestamp: 1710844379 Timestamp [UCT]: 2024-03-19 10:32:59 Age [y:d:h:m:s]: 01:048:16:09:06
Block: 981667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295768 RingCT/type: yes/0
Extra: 014d3df6e69dbf0658d55680ba6e18b40234d9c3b1506c8d7e89a2be29a0eb1dde02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e0fb7612b6434993b8e11d5c93eb48284e0b44ad9ceeaebe0d1158e4cfb708 0.600000000000 1441764 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": 981677, "vin": [ { "gen": { "height": 981667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e0fb7612b6434993b8e11d5c93eb48284e0b44ad9ceeaebe0d1158e4cfb708" } } ], "extra": [ 1, 77, 61, 246, 230, 157, 191, 6, 88, 213, 86, 128, 186, 110, 24, 180, 2, 52, 217, 195, 177, 80, 108, 141, 126, 137, 162, 190, 41, 160, 235, 29, 222, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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