Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be24c2471744eccc500263465a88ae7bc561f5c35b3cb3d4c12e69e80777729e

Tx prefix hash: e13c1a8c58558b486dca8c5923f51f8be015b2d39adf39add9d765d537ade37c
Tx public key: def3db2170d85459d53440b66421c68aea4d223a3af0dc601cb3e1b649abef62
Timestamp: 1722223810 Timestamp [UCT]: 2024-07-29 03:30:10 Age [y:d:h:m:s]: 00:323:22:53:59
Block: 1075991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231364 RingCT/type: yes/0
Extra: 01def3db2170d85459d53440b66421c68aea4d223a3af0dc601cb3e1b649abef620211000000026d122494000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc753ad69f68d06272d904cd0dcf1cbedc4ae5d3b183003394411bbb20510e61 0.600000000000 1548526 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": 1076001, "vin": [ { "gen": { "height": 1075991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc753ad69f68d06272d904cd0dcf1cbedc4ae5d3b183003394411bbb20510e61" } } ], "extra": [ 1, 222, 243, 219, 33, 112, 216, 84, 89, 213, 52, 64, 182, 100, 33, 198, 138, 234, 77, 34, 58, 58, 240, 220, 96, 28, 179, 225, 182, 73, 171, 239, 98, 2, 17, 0, 0, 0, 2, 109, 18, 36, 148, 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