Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a198a79a229d7cb04faece7995b3da1053ba25968f110deb61f51edb11fba84

Tx prefix hash: 412a58effe8729596cfabbf3faa2b944c10f42b1e5eac8dfaede4bd002c90845
Tx public key: 7e54c19c3f63b07022e1989c7466c45bc1cd669606f5e5a9b30ed43a2db9ad7e
Timestamp: 1696984993 Timestamp [UCT]: 2023-10-11 00:43:13 Age [y:d:h:m:s]: 01:247:05:58:03
Block: 866963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437701 RingCT/type: yes/0
Extra: 017e54c19c3f63b07022e1989c7466c45bc1cd669606f5e5a9b30ed43a2db9ad7e02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.822984620000 dcy

stealth address amount amount idx
00: 97e71a82d83c06706bc8cfe902629315b9f171fa4e10fcae51417e22e388ebf8 0.822984620000 1321603 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": 866973, "vin": [ { "gen": { "height": 866963 } } ], "vout": [ { "amount": 822984620, "target": { "key": "97e71a82d83c06706bc8cfe902629315b9f171fa4e10fcae51417e22e388ebf8" } } ], "extra": [ 1, 126, 84, 193, 156, 63, 99, 176, 112, 34, 225, 152, 156, 116, 102, 196, 91, 193, 205, 102, 150, 6, 245, 229, 169, 179, 14, 212, 58, 45, 185, 173, 126, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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