Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8021b40b13c9b626f2fa59f3cbd1cb7624bcd1f45a1a890dfc257f85e7cd45b

Tx prefix hash: 38d898f400edd4f828554b500218c29331fb9402508082e2a2d60b6561b4e161
Tx public key: bfef326ef51ef59e3ada22035d657613858ce5b08fabc27e317af031ddc3cfc0
Timestamp: 1696879953 Timestamp [UCT]: 2023-10-09 19:32:33 Age [y:d:h:m:s]: 01:136:20:39:51
Block: 866090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358799 RingCT/type: yes/0
Extra: 01bfef326ef51ef59e3ada22035d657613858ce5b08fabc27e317af031ddc3cfc00211000000064b8f5122000000000000000000

1 output(s) for total of 0.828484394000 dcy

stealth address amount amount idx
00: eb8e141b6c3e45e06c9677a8d1fcad6fa471b482f75bbed49b4a7fb7a6a37889 0.828484394000 1320658 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": 866100, "vin": [ { "gen": { "height": 866090 } } ], "vout": [ { "amount": 828484394, "target": { "key": "eb8e141b6c3e45e06c9677a8d1fcad6fa471b482f75bbed49b4a7fb7a6a37889" } } ], "extra": [ 1, 191, 239, 50, 110, 245, 30, 245, 158, 58, 218, 34, 3, 93, 101, 118, 19, 133, 140, 229, 176, 143, 171, 194, 126, 49, 122, 240, 49, 221, 195, 207, 192, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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