Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4eacb601b006ea79f05c14bbb36d22a16b23d341f9ea37455d893d20e1ed5ab

Tx prefix hash: 808a4fab6cde8cac0c79e364c035f97673b4a2d84dbc04a6e8f472f1efe6ca67
Tx public key: 555f25f899c4a29866275dfb6563f1bf0c09eb5d5ee51478bd74a77faa90ae35
Timestamp: 1716108041 Timestamp [UCT]: 2024-05-19 08:40:41 Age [y:d:h:m:s]: 01:035:07:57:49
Block: 1025299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285954 RingCT/type: yes/0
Extra: 01555f25f899c4a29866275dfb6563f1bf0c09eb5d5ee51478bd74a77faa90ae3502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64103060eec39f3c5f34e94323d15f3eb14e3548329fb9fa53174adf9793148d 0.600000000000 1491700 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": 1025309, "vin": [ { "gen": { "height": 1025299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64103060eec39f3c5f34e94323d15f3eb14e3548329fb9fa53174adf9793148d" } } ], "extra": [ 1, 85, 95, 37, 248, 153, 196, 162, 152, 102, 39, 93, 251, 101, 99, 241, 191, 12, 9, 235, 93, 94, 229, 20, 120, 189, 116, 167, 127, 170, 144, 174, 53, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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