Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef6d0652de2a7869a8b3989f8c404488eda7b077192198f03322c17b3f636d5

Tx prefix hash: d3331fbd16456ecf7a166ce5e884bd1bb4946fd26ccc36c3c9008ec51939ce61
Tx public key: f44ba908826b07b93869b5dcde59a82654a08356276fa4182aa43a3463c1b737
Timestamp: 1699058984 Timestamp [UCT]: 2023-11-04 00:49:44 Age [y:d:h:m:s]: 01:221:12:48:51
Block: 884150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419322 RingCT/type: yes/0
Extra: 01f44ba908826b07b93869b5dcde59a82654a08356276fa4182aa43a3463c1b737021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.721845126000 dcy

stealth address amount amount idx
00: f38f2b993094ae8bc7ff31f043a3209336cbe8f58ebcaafdce42b355e0ca15ab 0.721845126000 1339883 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": 884160, "vin": [ { "gen": { "height": 884150 } } ], "vout": [ { "amount": 721845126, "target": { "key": "f38f2b993094ae8bc7ff31f043a3209336cbe8f58ebcaafdce42b355e0ca15ab" } } ], "extra": [ 1, 244, 75, 169, 8, 130, 107, 7, 185, 56, 105, 181, 220, 222, 89, 168, 38, 84, 160, 131, 86, 39, 111, 164, 24, 42, 164, 58, 52, 99, 193, 183, 55, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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