Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eff3d7d2b35107360fc0353a5dfce931d73a48e41865b6b41581f8d7b11fbcb

Tx prefix hash: d1289f7dc790cd9f08535c2ef4bbcb2f8687b4084ee6150487140d97c7c28150
Tx public key: 851fc547992b2c2b969ff3cf1f8b0100f1e7782a447fa781293cd181e6ae453e
Timestamp: 1731768387 Timestamp [UCT]: 2024-11-16 14:46:27 Age [y:d:h:m:s]: 00:133:15:30:31
Block: 1155028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95334 RingCT/type: yes/0
Extra: 01851fc547992b2c2b969ff3cf1f8b0100f1e7782a447fa781293cd181e6ae453e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9538527cecebfc65af48dd2f715e0831f803e4438586de6354f47d4ad49b983 0.600000000000 1640641 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": 1155038, "vin": [ { "gen": { "height": 1155028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9538527cecebfc65af48dd2f715e0831f803e4438586de6354f47d4ad49b983" } } ], "extra": [ 1, 133, 31, 197, 71, 153, 43, 44, 43, 150, 159, 243, 207, 31, 139, 1, 0, 241, 231, 120, 42, 68, 127, 167, 129, 41, 60, 209, 129, 230, 174, 69, 62, 2, 17, 0, 0, 0, 4, 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