Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebaa9ee88eb6e70197d0d7f2927ef599877612bbf2778f36da9e4fdc1b213a8

Tx prefix hash: 6e17a65f9dc1ef59f02f120bad01ea581242dac75ee990a7180ab29ccfaecd25
Tx public key: 3689bb25145c4a65b0c6c7eb1575631a38875c7dd0b64d0617ebe0a595cd7873
Timestamp: 1702923232 Timestamp [UCT]: 2023-12-18 18:13:52 Age [y:d:h:m:s]: 01:139:02:03:28
Block: 915982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360543 RingCT/type: yes/0
Extra: 013689bb25145c4a65b0c6c7eb1575631a38875c7dd0b64d0617ebe0a595cd787302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aebee6af515d31e0af4c3793b8bac1c3d38e31bb991071cffcfc91e2e7a0b03d 0.600000000000 1373416 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": 915992, "vin": [ { "gen": { "height": 915982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aebee6af515d31e0af4c3793b8bac1c3d38e31bb991071cffcfc91e2e7a0b03d" } } ], "extra": [ 1, 54, 137, 187, 37, 20, 92, 74, 101, 176, 198, 199, 235, 21, 117, 99, 26, 56, 135, 92, 125, 208, 182, 77, 6, 23, 235, 224, 165, 149, 205, 120, 115, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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