Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4117a29f80e414e8de50ac65da8e1dc8951f3d647eb4987e7b5076d6a3654c8a

Tx prefix hash: 2badfc195b196c83fec639773ecb2b2ae6b90af4d86e09b9667145c93221fe6b
Tx public key: 3489f44b860a4da2b2c83f282ee8f54fb6de2122b92b9402e2d44465c10fd2af
Timestamp: 1714453889 Timestamp [UCT]: 2024-04-30 05:11:29 Age [y:d:h:m:s]: 00:327:04:20:54
Block: 1011572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233886 RingCT/type: yes/0
Extra: 013489f44b860a4da2b2c83f282ee8f54fb6de2122b92b9402e2d44465c10fd2af0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c74ff63f09e7b5dc3c7db51f68cb7ccb0182b6f9c2c7ee1168f807a6549a4842 0.600000000000 1473838 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": 1011582, "vin": [ { "gen": { "height": 1011572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c74ff63f09e7b5dc3c7db51f68cb7ccb0182b6f9c2c7ee1168f807a6549a4842" } } ], "extra": [ 1, 52, 137, 244, 75, 134, 10, 77, 162, 178, 200, 63, 40, 46, 232, 245, 79, 182, 222, 33, 34, 185, 43, 148, 2, 226, 212, 68, 101, 193, 15, 210, 175, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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