Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad7675569a7d115a3bc24ab635c9a10b83de782fb9ede708f40a9c232803500

Tx prefix hash: 55d8f38c5adf8f5fd8b7a4c8fc6c82fa4317632d8729c986a02f34a76da3f067
Tx public key: a7ba81080a493bcb7effb8db703611cb4bbb6084c5df1ecacb77e2f394e43e86
Timestamp: 1738062617 Timestamp [UCT]: 2025-01-28 11:10:17 Age [y:d:h:m:s]: 00:139:01:45:11
Block: 1206897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99354 RingCT/type: yes/0
Extra: 01a7ba81080a493bcb7effb8db703611cb4bbb6084c5df1ecacb77e2f394e43e8602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41eb254129d4be734bad70eb8e0b0c244324288d2b1120fc05acee5fdb85018e 0.600000000000 1693610 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": 1206907, "vin": [ { "gen": { "height": 1206897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41eb254129d4be734bad70eb8e0b0c244324288d2b1120fc05acee5fdb85018e" } } ], "extra": [ 1, 167, 186, 129, 8, 10, 73, 59, 203, 126, 255, 184, 219, 112, 54, 17, 203, 75, 187, 96, 132, 197, 223, 30, 202, 203, 119, 226, 243, 148, 228, 62, 134, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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