Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691b8fb563c3a9d2936600f41c0990b4c9a60be5e4d0fd4263f33796903b372b

Tx prefix hash: 225fd92d0f189fbf9d490a95f888473a9cc6ef4859621cb877063c1bb426685d
Tx public key: 05279dd4a7f8e2d43a195de8f24e9f297dd8d04d103cbac695392ce60e804eee
Timestamp: 1702231299 Timestamp [UCT]: 2023-12-10 18:01:39 Age [y:d:h:m:s]: 01:037:06:00:50
Block: 910248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287980 RingCT/type: yes/0
Extra: 0105279dd4a7f8e2d43a195de8f24e9f297dd8d04d103cbac695392ce60e804eee02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e7a562a764d467d0768f81c1e2f4873553df1199018288d3b3059ab7e4164db 0.600000000000 1367393 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": 910258, "vin": [ { "gen": { "height": 910248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e7a562a764d467d0768f81c1e2f4873553df1199018288d3b3059ab7e4164db" } } ], "extra": [ 1, 5, 39, 157, 212, 167, 248, 226, 212, 58, 25, 93, 232, 242, 78, 159, 41, 125, 216, 208, 77, 16, 60, 186, 198, 149, 57, 44, 230, 14, 128, 78, 238, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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