Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557d5fb9a24d66d4486305be5050dd43d44112ffd0c94352aece28b8075b88b8

Tx prefix hash: 9691f3a02f5566e66ae41008486768b1a299cacaec5c044576d3f828aa8bccb0
Tx public key: 30e3cfb2ad75e029e8c8f2bfdd823f8128dd90464ba58fbc74376d4e25fc4809
Timestamp: 1732693047 Timestamp [UCT]: 2024-11-27 07:37:27 Age [y:d:h:m:s]: 00:154:09:22:40
Block: 1162696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110157 RingCT/type: yes/0
Extra: 0130e3cfb2ad75e029e8c8f2bfdd823f8128dd90464ba58fbc74376d4e25fc4809021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d50b42b53388dd43e14159b6e0ee1e8135e5ab4e9650a0e1576266405a934f83 0.600000000000 1648353 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": 1162706, "vin": [ { "gen": { "height": 1162696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d50b42b53388dd43e14159b6e0ee1e8135e5ab4e9650a0e1576266405a934f83" } } ], "extra": [ 1, 48, 227, 207, 178, 173, 117, 224, 41, 232, 200, 242, 191, 221, 130, 63, 129, 40, 221, 144, 70, 75, 165, 143, 188, 116, 55, 109, 78, 37, 252, 72, 9, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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