Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9fa53071c065d9751aa0db35982d7d329426e97fb3d7418c6d335ba160b2ea

Tx prefix hash: cbc6d84339cbfaf44a38768b493c19f923d005d15efacb22514737395b47db35
Tx public key: a0553fc4ba9a678d15551b0c7f6184941364de69d8719b65fd81364fc9acc7ca
Timestamp: 1720400095 Timestamp [UCT]: 2024-07-08 00:54:55 Age [y:d:h:m:s]: 00:276:21:54:58
Block: 1060870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197849 RingCT/type: yes/0
Extra: 01a0553fc4ba9a678d15551b0c7f6184941364de69d8719b65fd81364fc9acc7ca02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdc27adc016b4cd4d1d7b353d2fd1f35ce379c9f591c6dfa6a292d2744748ed4 0.600000000000 1531357 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": 1060880, "vin": [ { "gen": { "height": 1060870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc27adc016b4cd4d1d7b353d2fd1f35ce379c9f591c6dfa6a292d2744748ed4" } } ], "extra": [ 1, 160, 85, 63, 196, 186, 154, 103, 141, 21, 85, 27, 12, 127, 97, 132, 148, 19, 100, 222, 105, 216, 113, 155, 101, 253, 129, 54, 79, 201, 172, 199, 202, 2, 17, 0, 0, 0, 2, 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