Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb56461ede37ae1438b70a9950fb2c9bbb6e7d68c8351bd957b24fbcfc15bb61

Tx prefix hash: dd10426185ed9a50d4b4067cc34f771618836fd204545afacfcba3dc749b00e0
Tx public key: 2d2b8a243548040700d2283295220ec76d0d564620af370c9a59e3a0bf527aea
Timestamp: 1712158106 Timestamp [UCT]: 2024-04-03 15:28:26 Age [y:d:h:m:s]: 01:032:07:10:20
Block: 992520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284078 RingCT/type: yes/0
Extra: 012d2b8a243548040700d2283295220ec76d0d564620af370c9a59e3a0bf527aea02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a393a1628daeee4349b1e4bfc3b29a3a0009e9fd63534ddd504c09d511b08c3c 0.600000000000 1452866 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": 992530, "vin": [ { "gen": { "height": 992520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a393a1628daeee4349b1e4bfc3b29a3a0009e9fd63534ddd504c09d511b08c3c" } } ], "extra": [ 1, 45, 43, 138, 36, 53, 72, 4, 7, 0, 210, 40, 50, 149, 34, 14, 199, 109, 13, 86, 70, 32, 175, 55, 12, 154, 89, 227, 160, 191, 82, 122, 234, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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