Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60457aac530dd77cb95cfe702d1f4e481e1f50e533e27f9902ea3cfe9061a902

Tx prefix hash: 710dc6cc46f0ea598a04ff17e14926c16e1a6ce5ef752d7329ed30e6e02de776
Tx public key: d7997dff50ce433382528739c98d1aacc940d35dbcbf3b4ff85b61c8a0179b7b
Timestamp: 1711653852 Timestamp [UCT]: 2024-03-28 19:24:12 Age [y:d:h:m:s]: 01:045:20:28:11
Block: 988381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293740 RingCT/type: yes/0
Extra: 01d7997dff50ce433382528739c98d1aacc940d35dbcbf3b4ff85b61c8a0179b7b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25dafe801b74ddcde2bf04dc52a5bdc65791b374fc971ab02f91784bb4c0e738 0.600000000000 1448660 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": 988391, "vin": [ { "gen": { "height": 988381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25dafe801b74ddcde2bf04dc52a5bdc65791b374fc971ab02f91784bb4c0e738" } } ], "extra": [ 1, 215, 153, 125, 255, 80, 206, 67, 51, 130, 82, 135, 57, 201, 141, 26, 172, 201, 64, 211, 93, 188, 191, 59, 79, 248, 91, 97, 200, 160, 23, 155, 123, 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