Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e3cf8f6f615e35c69bc3388b33d561eb3751d2ce32bec1aa2f727cefcc6974

Tx prefix hash: 611c587dd3390454d1e7d5c771af899b1dc304adec79025d51235d0048359184
Tx public key: 2a34f24df456ef99f8a3e0b97ed9711c99ef35223c95d64bb3b5ccc9f386fa41
Timestamp: 1706580215 Timestamp [UCT]: 2024-01-30 02:03:35 Age [y:d:h:m:s]: 01:029:00:58:21
Block: 946279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281802 RingCT/type: yes/0
Extra: 012a34f24df456ef99f8a3e0b97ed9711c99ef35223c95d64bb3b5ccc9f386fa410211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beb73544a6056e5d0d57c8c5ed71ddbeb32b3ad0c0b9e7caf6a65934364763b3 0.600000000000 1404611 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": 946289, "vin": [ { "gen": { "height": 946279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beb73544a6056e5d0d57c8c5ed71ddbeb32b3ad0c0b9e7caf6a65934364763b3" } } ], "extra": [ 1, 42, 52, 242, 77, 244, 86, 239, 153, 248, 163, 224, 185, 126, 217, 113, 28, 153, 239, 53, 34, 60, 149, 214, 75, 179, 181, 204, 201, 243, 134, 250, 65, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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