Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 270f658d366c4318bddaec65e6c403135009f1dbaa3306e716b0b6b943700514

Tx prefix hash: e73826e0af0e8fc672f3950792f2c2c9afc36c29357f67d8e8763ee55e4e9bdf
Tx public key: 46ce1f7be69a7bff2541791c228fb97acc7139f44efd9817aa69682bdd03dbb4
Timestamp: 1696347195 Timestamp [UCT]: 2023-10-03 15:33:15 Age [y:d:h:m:s]: 01:223:02:48:44
Block: 861664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420542 RingCT/type: yes/0
Extra: 0146ce1f7be69a7bff2541791c228fb97acc7139f44efd9817aa69682bdd03dbb402110000000136a45730000000000000000000

1 output(s) for total of 0.856938221000 dcy

stealth address amount amount idx
00: d46be26d44c3bded398584c6ea41c12e5736dc58c5665a406d6e811d6b7fa911 0.856938221000 1316024 of 0

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": 861674, "vin": [ { "gen": { "height": 861664 } } ], "vout": [ { "amount": 856938221, "target": { "key": "d46be26d44c3bded398584c6ea41c12e5736dc58c5665a406d6e811d6b7fa911" } } ], "extra": [ 1, 70, 206, 31, 123, 230, 154, 123, 255, 37, 65, 121, 28, 34, 143, 185, 122, 204, 113, 57, 244, 78, 253, 152, 23, 170, 105, 104, 43, 221, 3, 219, 180, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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