Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47015c6523eba501566d84cae0baf9ebdb518634ac2d0e7e14cb4c04a5928fb0

Tx prefix hash: 58963eea610930cb309e488e58623722369dba6322fc90616220fdf04daac346
Tx public key: 938a8e9223b7df15bd13a0bd9e08b5ccfdd05e8661309bf4fa28737c0b4c9c58
Timestamp: 1740415316 Timestamp [UCT]: 2025-02-24 16:41:56 Age [y:d:h:m:s]: 00:270:07:19:56
Block: 1226347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190947 RingCT/type: yes/0
Extra: 01938a8e9223b7df15bd13a0bd9e08b5ccfdd05e8661309bf4fa28737c0b4c9c5802110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fdf0937ea9b9bdd7c09d5ff1dc04d3e7518038cb5ad953efaa2842bbbdc3698 0.600000000000 1713218 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": 1226357, "vin": [ { "gen": { "height": 1226347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fdf0937ea9b9bdd7c09d5ff1dc04d3e7518038cb5ad953efaa2842bbbdc3698" } } ], "extra": [ 1, 147, 138, 142, 146, 35, 183, 223, 21, 189, 19, 160, 189, 158, 8, 181, 204, 253, 208, 94, 134, 97, 48, 155, 244, 250, 40, 115, 124, 11, 76, 156, 88, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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