Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b9f6eabfb569d3f2e18ce0b2351bf0f3686ed01efdc28e0abb170b34c73b907

Tx prefix hash: 98e7f87c548a715313a10b6349b6d3cbed4f44f60519d7b4487b6b770348bc66
Tx public key: b72e9d484553eca332228b1be35b3538537ffb2d501286c613aa1d47bdc324cc
Timestamp: 1648501552 Timestamp [UCT]: 2022-03-28 21:05:52 Age [y:d:h:m:s]: 03:217:11:57:16
Block: 468465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933365 RingCT/type: yes/0
Extra: 01b72e9d484553eca332228b1be35b3538537ffb2d501286c613aa1d47bdc324cc0211000000054a0f5013000000000000000000

1 output(s) for total of 17.210014556000 dcy

stealth address amount amount idx
00: 3587025ef5f4c6d5310a86c61a933fe80b5565e75431f8140ec5e6d3ad24a6f9 17.210014556000 887189 of 0

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": 468475, "vin": [ { "gen": { "height": 468465 } } ], "vout": [ { "amount": 17210014556, "target": { "key": "3587025ef5f4c6d5310a86c61a933fe80b5565e75431f8140ec5e6d3ad24a6f9" } } ], "extra": [ 1, 183, 46, 157, 72, 69, 83, 236, 163, 50, 34, 139, 27, 227, 91, 53, 56, 83, 127, 251, 45, 80, 18, 134, 198, 19, 170, 29, 71, 189, 195, 36, 204, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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