Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4785d9bfc8407d1fba10c6a1a92f3c53629ff9c54d3623ca267a70006f666612

Tx prefix hash: 9d5ee2456b40945044d689fa989aa63f1d6470b7521bd7d19340bb9af2cb3377
Tx public key: 1a28a9d379ab39219e96ad0c11f70c652a63d4903ecbeac2a58fd2ed8958a744
Timestamp: 1578439301 Timestamp [UCT]: 2020-01-07 23:21:41 Age [y:d:h:m:s]: 05:067:16:31:51
Block: 40844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198386 RingCT/type: yes/0
Extra: 011a28a9d379ab39219e96ad0c11f70c652a63d4903ecbeac2a58fd2ed8958a74402110000000717786bcf000000000000000000

1 output(s) for total of 449.445597821000 dcy

stealth address amount amount idx
00: e996b566fcc3d98adb89db0261ae5b897039f5d23eb1c2efbb28b3fb53a5f670 449.445597821000 72137 of 0

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": 40854, "vin": [ { "gen": { "height": 40844 } } ], "vout": [ { "amount": 449445597821, "target": { "key": "e996b566fcc3d98adb89db0261ae5b897039f5d23eb1c2efbb28b3fb53a5f670" } } ], "extra": [ 1, 26, 40, 169, 211, 121, 171, 57, 33, 158, 150, 173, 12, 17, 247, 12, 101, 42, 99, 212, 144, 62, 203, 234, 194, 165, 143, 210, 237, 137, 88, 167, 68, 2, 17, 0, 0, 0, 7, 23, 120, 107, 207, 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