Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c92d3bbacdfc2076581bc09d2f23f98dbf01d46d81df83fc2f429f2a21f6b9c

Tx prefix hash: 2d608799ce1726abe6572381bc6dfd51367c6f3731b074db0872c201cb0c81bf
Tx public key: 380fb33ded330c9692c9eff95df7c874e9bf9dab759d6b254a0a1219f9f267ae
Timestamp: 1709273055 Timestamp [UCT]: 2024-03-01 06:04:15 Age [y:d:h:m:s]: 01:221:01:51:00
Block: 968631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416675 RingCT/type: yes/0
Extra: 01380fb33ded330c9692c9eff95df7c874e9bf9dab759d6b254a0a1219f9f267ae02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 947e39617486e2fc44469b66d9573fc9ecf5ff546ab7313e2a35f3d8fd70771c 0.600000000000 1428448 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": 968641, "vin": [ { "gen": { "height": 968631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "947e39617486e2fc44469b66d9573fc9ecf5ff546ab7313e2a35f3d8fd70771c" } } ], "extra": [ 1, 56, 15, 179, 61, 237, 51, 12, 150, 146, 201, 239, 249, 93, 247, 200, 116, 233, 191, 157, 171, 117, 157, 107, 37, 74, 10, 18, 25, 249, 242, 103, 174, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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