Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c809037951d186e930fa7c78838a4cc0f2e9ac7499c011e6c502cc85a7f177cf

Tx prefix hash: 30a6e409960ba74caed278f0776e2e3fe5e032390441e680428b236943aa5727
Tx public key: 4e331454d8aa93a0d08879cc7bf3e8704cc928a112f5c5894927511cb81e2789
Timestamp: 1712158572 Timestamp [UCT]: 2024-04-03 15:36:12 Age [y:d:h:m:s]: 01:058:20:00:36
Block: 992526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303073 RingCT/type: yes/0
Extra: 014e331454d8aa93a0d08879cc7bf3e8704cc928a112f5c5894927511cb81e27890211000000013f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a508e7439642b0c2626eb4046231b7dcec797da1a5e5f0170e0ccf2684bd8e7 0.600000000000 1452872 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": 992536, "vin": [ { "gen": { "height": 992526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a508e7439642b0c2626eb4046231b7dcec797da1a5e5f0170e0ccf2684bd8e7" } } ], "extra": [ 1, 78, 51, 20, 84, 216, 170, 147, 160, 208, 136, 121, 204, 123, 243, 232, 112, 76, 201, 40, 161, 18, 245, 197, 137, 73, 39, 81, 28, 184, 30, 39, 137, 2, 17, 0, 0, 0, 1, 63, 130, 249, 251, 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