Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b787576c7e356e75e190b9934635f9e5ecd929b17b2af8000f29ef3cd9be52

Tx prefix hash: 73fb450f52832c46e8c64afcaf8e588a2dfa3eea1f976668ee4190bc718dfbc6
Tx public key: 8702d2fbcde25201319a419f33f1a1599e4dfa748052fd03183ffff640be035c
Timestamp: 1724606984 Timestamp [UCT]: 2024-08-25 17:29:44 Age [y:d:h:m:s]: 00:227:19:10:32
Block: 1095747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162675 RingCT/type: yes/0
Extra: 018702d2fbcde25201319a419f33f1a1599e4dfa748052fd03183ffff640be035c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7a098b73e770f9b60f9dfbbfe36afe893a4a598e45eab9e9784a00c644a1b4c 0.600000000000 1570928 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": 1095757, "vin": [ { "gen": { "height": 1095747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7a098b73e770f9b60f9dfbbfe36afe893a4a598e45eab9e9784a00c644a1b4c" } } ], "extra": [ 1, 135, 2, 210, 251, 205, 226, 82, 1, 49, 154, 65, 159, 51, 241, 161, 89, 158, 77, 250, 116, 128, 82, 253, 3, 24, 63, 255, 246, 64, 190, 3, 92, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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