Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecb28f67b8da4cac323ce4ef5f112faa5c4c5025b5aef8f8a46c6b9f7491001e

Tx prefix hash: 3556b613943f01a4d67484333634ab77ee9dc9d2f789f228810f2427cc8ddb84
Tx public key: 8738f37a603eb20757507e6ca7d0fa3fe2ceedb4f472591251c6ef046487a6c1
Timestamp: 1720290801 Timestamp [UCT]: 2024-07-06 18:33:21 Age [y:d:h:m:s]: 00:313:02:34:54
Block: 1059965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223756 RingCT/type: yes/0
Extra: 018738f37a603eb20757507e6ca7d0fa3fe2ceedb4f472591251c6ef046487a6c10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f5f23455719ba4f77758f3a01d3e5ad9c97c338573941adc5a2a2906a15794 0.600000000000 1530436 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": 1059975, "vin": [ { "gen": { "height": 1059965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f5f23455719ba4f77758f3a01d3e5ad9c97c338573941adc5a2a2906a15794" } } ], "extra": [ 1, 135, 56, 243, 122, 96, 62, 178, 7, 87, 80, 126, 108, 167, 208, 250, 63, 226, 206, 237, 180, 244, 114, 89, 18, 81, 198, 239, 4, 100, 135, 166, 193, 2, 17, 0, 0, 0, 7, 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