Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768bbcde0dd1ed2cd0b8188a4873ba13a668d7adbff2fb788408ce417ee25c14

Tx prefix hash: 27c414615639d92854f48ee1ee16336409120b5a2eb26a1e61b55371fe5b02e3
Tx public key: 613cae7aae69356b6b21e02488938acd2b763ff2809e7b67b3b0b21a27eb1924
Timestamp: 1721376002 Timestamp [UCT]: 2024-07-19 08:00:02 Age [y:d:h:m:s]: 00:248:01:19:46
Block: 1068975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177183 RingCT/type: yes/0
Extra: 01613cae7aae69356b6b21e02488938acd2b763ff2809e7b67b3b0b21a27eb192402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aad886269e39d8f83554dea8857c6cbbeed5cba005a2414a782c2c0643d7a18 0.600000000000 1540218 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": 1068985, "vin": [ { "gen": { "height": 1068975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aad886269e39d8f83554dea8857c6cbbeed5cba005a2414a782c2c0643d7a18" } } ], "extra": [ 1, 97, 60, 174, 122, 174, 105, 53, 107, 107, 33, 224, 36, 136, 147, 138, 205, 43, 118, 63, 242, 128, 158, 123, 103, 179, 176, 178, 26, 39, 235, 25, 36, 2, 17, 0, 0, 0, 5, 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