Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77111913f12fe9dc8148e1493fed06623817258ab8461b4e5e38ddc5680e6095

Tx prefix hash: 1f7392815465c42194daea282b32fb5dc5136e59f0ffd3c1085cff3eda8bf1d0
Tx public key: 1e0bc0beda7ec860e95dab61af087b16356310b5e09ea5cca6c9dc8a7b524c8b
Timestamp: 1723127499 Timestamp [UCT]: 2024-08-08 14:31:39 Age [y:d:h:m:s]: 00:152:09:00:32
Block: 1083473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109014 RingCT/type: yes/0
Extra: 011e0bc0beda7ec860e95dab61af087b16356310b5e09ea5cca6c9dc8a7b524c8b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f948585d3fbd50945f45a510248af635b19f7326b07620b6541d776476bb721c 0.600000000000 1557408 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": 1083483, "vin": [ { "gen": { "height": 1083473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f948585d3fbd50945f45a510248af635b19f7326b07620b6541d776476bb721c" } } ], "extra": [ 1, 30, 11, 192, 190, 218, 126, 200, 96, 233, 93, 171, 97, 175, 8, 123, 22, 53, 99, 16, 181, 224, 158, 165, 204, 166, 201, 220, 138, 123, 82, 76, 139, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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