Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc9474487b2c3bb094354198cacdf17d129019cf3b2e624b8add3f5a13e68f6

Tx prefix hash: 4fa78df9eeb969c0c16d2f94e7bccc11cbb5268a0e326f00d67ca49a636d95b4
Tx public key: 3d9f7c16ddfa84be865605e8cc6a3668c4ff380cc879da4f86caa74e17286911
Timestamp: 1717232780 Timestamp [UCT]: 2024-06-01 09:06:20 Age [y:d:h:m:s]: 01:020:08:53:01
Block: 1034624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275298 RingCT/type: yes/0
Extra: 013d9f7c16ddfa84be865605e8cc6a3668c4ff380cc879da4f86caa74e17286911021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cfdef9c9a1e19fdc839e0d1b7ae0e0335aa8676019ce1df8b397675a757ed79 0.600000000000 1503137 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": 1034634, "vin": [ { "gen": { "height": 1034624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cfdef9c9a1e19fdc839e0d1b7ae0e0335aa8676019ce1df8b397675a757ed79" } } ], "extra": [ 1, 61, 159, 124, 22, 221, 250, 132, 190, 134, 86, 5, 232, 204, 106, 54, 104, 196, 255, 56, 12, 200, 121, 218, 79, 134, 202, 167, 78, 23, 40, 105, 17, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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