Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82ae936dfe64f78077b662fc58fdf98b2205817e83f319958e8d0277c590ee71

Tx prefix hash: c22e861f286ffa8d270d85c0d8d8454412965918bf5393b92f32dd457f444987
Tx public key: bd3d765cf32b0e1fd2fb5dcb1041c5f206cf2ae66382b195883c15f30dffb147
Timestamp: 1722726214 Timestamp [UCT]: 2024-08-03 23:03:34 Age [y:d:h:m:s]: 00:140:19:06:26
Block: 1080154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100767 RingCT/type: yes/0
Extra: 01bd3d765cf32b0e1fd2fb5dcb1041c5f206cf2ae66382b195883c15f30dffb147021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e3c886a13ddb81cc8dc9ea07fa230a62af4e8c1aaa3cabeea2cb5f19d27f496 0.600000000000 1553407 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": 1080164, "vin": [ { "gen": { "height": 1080154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e3c886a13ddb81cc8dc9ea07fa230a62af4e8c1aaa3cabeea2cb5f19d27f496" } } ], "extra": [ 1, 189, 61, 118, 92, 243, 43, 14, 31, 210, 251, 93, 203, 16, 65, 197, 242, 6, 207, 42, 230, 99, 130, 177, 149, 136, 60, 21, 243, 13, 255, 177, 71, 2, 17, 0, 0, 0, 7, 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