Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f556dd7a9bc5c360ae10d7240a2ab949c83ca2386aebfa2ca7f99bcc118d2e

Tx prefix hash: 6d52d1027d5d45ab166ad2d7f18e459033186615cf0a4655c11709a3ea4340bf
Tx public key: e7711a8dcfe9ff658084c99d56c515d52f20a2edf0b2f8c6db88503b5613cdb0
Timestamp: 1722097324 Timestamp [UCT]: 2024-07-27 16:22:04 Age [y:d:h:m:s]: 01:104:04:45:11
Block: 1074941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332964 RingCT/type: yes/0
Extra: 01e7711a8dcfe9ff658084c99d56c515d52f20a2edf0b2f8c6db88503b5613cdb002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0baac01a54101f672af8aca6ce386b69b245323ecb040aa48d894acb264a177a 0.600000000000 1547460 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": 1074951, "vin": [ { "gen": { "height": 1074941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0baac01a54101f672af8aca6ce386b69b245323ecb040aa48d894acb264a177a" } } ], "extra": [ 1, 231, 113, 26, 141, 207, 233, 255, 101, 128, 132, 201, 157, 86, 197, 21, 213, 47, 32, 162, 237, 240, 178, 248, 198, 219, 136, 80, 59, 86, 19, 205, 176, 2, 17, 0, 0, 0, 7, 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