Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f15a5dd5c9b82e16bf1c7a47c2544f4c90a29bda301f73b79abc9954ddf18ab

Tx prefix hash: bc8a680a3f8c627ae9022d289dd2cc1842b332a7d38f732ffc9ef1e7f888e7a9
Tx public key: f74b2d50648ecede42e394256512497055d62f8bbfaef1bc7c4f733e8168365b
Timestamp: 1716277697 Timestamp [UCT]: 2024-05-21 07:48:17 Age [y:d:h:m:s]: 00:326:12:47:21
Block: 1026707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233380 RingCT/type: yes/0
Extra: 01f74b2d50648ecede42e394256512497055d62f8bbfaef1bc7c4f733e8168365b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb83ebffc4e8c35ab340ba12bd3afd59e7f3c19c6dd3040e4a31c3a0e358c2ef 0.600000000000 1493936 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": 1026717, "vin": [ { "gen": { "height": 1026707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb83ebffc4e8c35ab340ba12bd3afd59e7f3c19c6dd3040e4a31c3a0e358c2ef" } } ], "extra": [ 1, 247, 75, 45, 80, 100, 142, 206, 222, 66, 227, 148, 37, 101, 18, 73, 112, 85, 214, 47, 139, 191, 174, 241, 188, 124, 79, 115, 62, 129, 104, 54, 91, 2, 17, 0, 0, 0, 1, 82, 212, 126, 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